Description

Enhances the run command output to display service URLs immediately after services start, improving actionability by giving users direct access to their deployed services.

Closes #334

Changes

Phase 1: Shared View Components ✅

• Created src/presentation/views/commands/shared/service_urls/ module
• CompactServiceUrlsView - Renders service URLs in compact format (10 unit tests)
• DnsHintView - Provides DNS configuration hints for HTTPS services (5 unit tests)
• All 15 tests passing

Phase 2: Enhanced Run Command Output ✅

• Modified RunCommandController::complete_workflow() to display service URLs
• Added display_service_urls() method using shared views
• Added load_environment() method reusing show command pattern
• Added From<RepositoryError> conversion for proper error handling
• All 2210 tests passing

Phase 3: Documentation ✅

• Updated docs/user-guide/commands/run.md with new output examples
• Updated docs/console-commands.md with new output format
• Issue specification marked complete with all acceptance criteria

Sample Output

Run Command (New Feature - HTTPS/TLS Environment)

$ cargo run -- run lxd-local-https-example

⏳ [1/2] Validating environment...
⏳   ✓ Environment name validated: lxd-local-https-example (took 0ms)
⏳ [2/2] Running application services...
⏳   ✓ Services started (took 24.0s)
✅ Run command completed for 'lxd-local-https-example'

Services are now accessible:
  Tracker (UDP):  udp://udp.tracker.local:6969/announce
  Tracker (HTTP): https://http.tracker.local/announce
  API:            https://api.tracker.local/api
  Health Check:   https://health.tracker.local/health_check
  Grafana:        https://grafana.tracker.local/


Note: HTTPS services require DNS configuration. See 'show' command for details.

Tip: Run 'torrust-tracker-deployer show lxd-local-https-example' for full details

Show Command (Comparison - Full Details)

$ cargo run -- show lxd-local-https-example

Environment: lxd-local-https-example
State: Running
Provider: LXD
Created: 2026-02-11 09:52:28 UTC

Infrastructure:
  Instance IP: 10.140.190.36
  SSH Port: 22
  SSH User: torrust
  SSH Key: /home/josecelano/Documents/git/committer/me/github/torrust/torrust-tracker-deployer-agent-01/fixtures/testing_rsa

Connection:
  ssh -i /home/josecelano/Documents/git/committer/me/github/torrust/torrust-tracker-deployer-agent-01/fixtures/testing_rsa torrust@10.140.190.36

Tracker Services:
  UDP Trackers:
    - udp://udp.tracker.local:6969/announce
  HTTP Trackers (HTTPS via Caddy):
    - https://http.tracker.local/announce
  API Endpoint (HTTPS via Caddy):
    - https://api.tracker.local/api
  Health Check (HTTPS via Caddy):
    - https://health.tracker.local/health_check

Prometheus:
  Internal only (localhost:9090) - not exposed externally

Grafana (HTTPS via Caddy):
  https://grafana.tracker.local/

Note: HTTPS services require domain-based access. For local domains (*.local),
add the following to your /etc/hosts file:

  10.140.190.36   http.tracker.local api.tracker.local grafana.tracker.local health.tracker.local

Internal ports (7070, 1212, 3000, 1313) are not directly accessible when TLS is enabled.

Services are running. Use 'test' to verify health.

Architecture

• DDD Layer: Presentation
• Module Path: src/presentation/views/commands/shared/service_urls/
• Pattern: View composition with shared components
• Design: Reuses shared views between run and show commands (no duplication)

Quality Assurance

• ✅ All linters passing: markdown, yaml, toml, cspell, clippy, rustfmt, shellcheck
• ✅ All 2210 unit tests passing
• ✅ E2E tests passing (infrastructure lifecycle + deployment workflow)
• ✅ Documentation builds successfully
• ✅ Pre-commit checks passing
• ✅ Manual E2E test verified with live deployment

Architecture Compliance

• ✅ Follows DDD layer separation (Presentation layer)
• ✅ Reuses shared view components (no duplication)
• ✅ Uses UserOutput methods (no println!)
• ✅ Output goes to stdout via ProgressReporter::result()
• ✅ Follows module organization conventions
• ✅ Error handling follows project conventions

Commits

1. feat: [#334] add shared service URL views - Phase 1: Shared view components
2. feat: [#334] display service URLs after run command completes - Phase 2: Enhanced output
3. docs: [#334] update run command documentation with service URLs - Phase 3: Documentation (part 1)
4. docs: [#334] mark implementation complete with all acceptance criteria - Phase 3: Documentation (part 2)

Testing

Verified with manual E2E test:

1. Configured environment: configure lxd-local-https-example
2. Released application: release lxd-local-https-example
3. Started services: run lxd-local-https-example ✅ New output displayed
4. Compared with: show lxd-local-https-example ✅ Full details shown

Rationale

1. Actionable - Users immediately know where to access services
2. Not overwhelming - Doesn't duplicate full show output (omits SSH details, internal ports)
3. Educational - Teaches users about the show command
4. Follows project principles - "Actionability: The system must always tell users how to continue"

The run command is the moment users want to use the services, so showing URLs immediately provides high value.